Tootfinder

#Google Public #DNS’s approach to fight against cache poisoning attacks #infosec

I'm having ridiculous plans.
Instead of moving the Starship and Tarot projects over to a temp instance, and then back to a re-built server with new software on the old domain... what if I just moved both of their websites to become GotoSocial websites?
They're both currently built with Hugo as static sites anyway, so they could drop into the Assets folder on a GotoSocial site if I accepted the /assets/ in the front of every URL, or renamed that in the source-code.
And with just a bit of template-editing for the homepage I've got essentially the entire old website plus the Fediverse/gotoSocial features on each project's own domain, the /@user URLs leading to an activity-pub feed of stuff I can boost from here.
Course, that means two new VMs/IP-addresses instead of using the existing one. Or I suppose running two GotoSocial processes and a front-end redirector of some sort...
Oh man. That's loads more work than I was hoping but it's obviously the right thing to do really.
They each need their own social site URLs not sharing one with my name.

I just found a great domain name. Free to register and very cheap.
But I have
- no idea what to use the domain for
- (almost) no time to maintain any kind of online service
- no need for any online domain in the first place
Life just sucks sometimes :-(

One of the fediverse's great strengths is that you can block entire collections of ill-intentioned morons at once. My own policy is to defederate any server with "shitpost" in the domain name.
If only I could do that to my "fuck your feelings" magat neighbors.

Damnit, I hate when I hit a new domain-name too early and it hasn't propagated enough and now my cache is not-found until fuck knows when, might as well get a drink.

Looking at Akkoma a bit.
Install was pretty persnickety, editing nginx config files by hand and having to stop Nginx while fetching ssl certs.
Apparently it needs to recompile at the slightest tweak of the config files? Strange decision.
Not really clear why I have to use pleroma.instance in the middle of the config. Initialy tried changing that to the name of my new test instance but apparently it isn't that. I guess "pleremoa.instance" is some kind of legacy config template from before Akkoma forked? Maybe?
Media-uploads apparently not working without further configuration. Wasn't sure why it insisted I put that in a different domain-name and then never told me how to configure to use that.
Doesn't seem likely this is the easiest activitypub server to manage after all.